From: Joey Hess Date: Tue, 23 Sep 2025 03:55:22 +0000 (-0400) Subject: thought X-Git-Tag: archive/raspbian/10.20251029-1+rpi1~1^2~3^2~74 X-Git-Url: https://dgit.raspbian.org/%22http://www.example.com/cgi/%22/%22http:/www.example.com/cgi/%22?a=commitdiff_plain;h=478f42d3f38733ebce2dd8674a9107565831f9e0;p=git-annex.git thought --- diff --git a/doc/bugs/annex_import_doesn__39__t_delete_files_during_updates/comment_3_8f6e2216765e610683a2684165c84201._comment b/doc/bugs/annex_import_doesn__39__t_delete_files_during_updates/comment_3_8f6e2216765e610683a2684165c84201._comment new file mode 100644 index 0000000000..c123fffa28 --- /dev/null +++ b/doc/bugs/annex_import_doesn__39__t_delete_files_during_updates/comment_3_8f6e2216765e610683a2684165c84201._comment @@ -0,0 +1,18 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 3""" + date="2025-09-23T03:52:45Z" + content=""" +Another way to think about this problem is that git-annex export does not +update the remote tracking branch. If it did, there would be no need for +git-annex import to learn about changes made by export, and its current +diffing behavior would be ok. + +However, since one repository can export to a special remote, and a +different repository import from the same special remote, updating the +tracking branch would need to happen later, based on information the export +records in the git-annex branch. + +Which is something that git-annex import could do. But it might not be any +more efficient to do that than a non-diff based update. +"""]]